To reiterate: You will see a branch “o486” in the OpenCPN github repo. That branch was captured at the point of release of 4.8.6. It will build the current production release, and will be forked again to contain critical backports if required. New work goes on in “master”.

The opencpn.org download page will generally point to “master” of the plugin repo for the source link. Presumably source builders will know which branch they need to pull for local builds. The download page will also point to built binaries that are compatible with the current release of base OCPN, whatever that may be at the time.

If/when we have a Beta underway that breaks compatibility, there will be another section of the .org site that provides links to plugin Beta binaries ready and available for test with the Beta base.